Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@build-logic/src/main/java/AndroidFeatureConventionPlugin.kt`:
- Line 26: The build uses implementation(libs.kotlinx.collections.immutable) but
FocusingSearchUiState exposes ImmutableList<CircleModel> publicly, so change the
dependency declaration to api(libs.kotlinx.collections.immutable) in the
AndroidFeatureConventionPlugin (the place where kotlinx-collections-immutable is
added) so the ImmutableList type is transitive and available on consumers'
compile classpath; update the dependency configuration from implementation to
api for kotlinx-collections-immutable to fix the missing type at compile time.

In
`@feature/detail/src/main/java/com/metasearch/android/feature/detail/graph/GraphDetailSideEffect.kt`:
- Around line 17-19: The GraphDetailSideEffect.ShowToast branch builds a
MetaSearchEvent.ShowToast but never dispatches it and lacks the EventHandler
import; update the branch in GraphDetailSideEffect (where
GraphDetailSideEffect.ShowToast is handled) to call
EventHandler.sendEvent(MetaSearchEvent.ShowToast(...)) instead of just
constructing the event, and add the missing import for EventHandler so the
sendEvent call compiles; follow the same pattern used in NLSearchSideEffect
(lines handling EventHandler.sendEvent) as a template.

In
`@feature/detail/src/main/java/com/metasearch/android/feature/detail/photo/PhotoDetailPresenter.kt`:
- Around line 97-101: Add a UUID-based key to the ShareImage side effect so
consecutive shares with the same uriString are not considered equal: modify the
PhotoDetailSideEffect.ShareImage data class to include a private val key: String
= UUID.randomUUID().toString() (and add import java.util.UUID) so existing
construction in PhotoDetailPresenter (handling
PhotoDetailUiEvent.OnShareImageButtonClick) can remain unchanged but each
instance is unique; mirror the pattern used by ShowToast for deduplication.

In `@feature/home/src/main/java/com/metasearch/android/feature/home/HomeUi.kt`:
- Around line 125-130: The offset lambda is using hardcoded pixel constants
(+20, -120) which breaks across screen densities; change those raw numbers to
dp-to-px conversions using the Density receiver available in the offset { }
lambda (e.g., call 20.dp.toPx() and 120.dp.toPx()) before converting to Int for
IntOffset so the offsets are consistent with state.selectedOffset (which comes
from coordinates.positionInRoot()) and then use (x = (state.selectedOffset.x +
convertedX).toInt(), y = (state.selectedOffset.y - convertedY).toInt()) inside
the offset block.
- Around line 118-155: The overlay content is removed immediately because
state.selectedLongClickImage is set to null before AnimatedVisibility's fadeOut
finishes; fix by introducing a local "last non-null" snapshot (e.g.,
lastSelectedLongClickImage) that you update when state.selectedLongClickImage
becomes non-null and continue to use that snapshot instead of
state.selectedLongClickImage inside the let block that renders Icon and
AsyncImage; clear the snapshot only after the exit animation completes (use
AnimatedVisibility's exit/onAnimationEnd callback or a LaunchedEffect keyed to
the visibility/animation) so the Icon and AsyncImage remain visible for the full
fadeOut when OnLongClickCancel fires.

In
`@feature/home/src/main/java/com/metasearch/android/feature/home/HomeUiState.kt`:
- Around line 25-30: HomeSideEffect.ShareImage currently lacks a uniqueness key
so emitting the same uriString twice produces an equal object and Compose won't
re-trigger the side effect; update the ShareImage data class inside
HomeSideEffect to include a private val key: String =
UUID.randomUUID().toString() (import java.util.UUID as needed) so each emission
is distinct while keeping uriString accessible.

In `@feature/home/src/main/res/drawable/ic_image_share.xml`:
- Around line 2-3: The drawable's intrinsic size is incorrectly large: replace
the android:width and android:height attributes set to "512dp" with the correct
icon size "24dp" so the vector's intrinsic dimensions match its viewport
(viewportWidth="24" and viewportHeight="24"); update the attributes in
ic_image_share.xml to android:width="24dp" and android:height="24dp" to prevent
the drawable from occupying 512dp when used with wrap_content or default
ImageView behavior.

In
`@feature/main/src/main/java/com/metasearch/android/feature/main/MainActivity.kt`:
- Around line 106-109: The toast currently passes a non-null empty string via
MetaSearchToast(message = toastMessage ?: ""), causing the message?.let { ... }
block in MetaSearchToast to run during exit animation; change the call to pass
the nullable value directly (message = toastMessage) so MetaSearchToast.message
(String? = null) can be null and the let block will be skipped when there is no
message.

In
`@feature/person/src/main/java/com/metasearch/android/feature/person/PersonPresenter.kt`:
- Around line 53-55: Replace the three delete-dialog state properties that
currently use remember with rememberRetained so the confirmation dialog and
pending values persist across configuration changes: update showDeleteDialog,
pendingDeletePersonId and pendingDeletePersonName to use rememberRetained
instead of remember (matching the existing usage for the search input and other
dialog state in PersonDetailPresenter) to prevent the dialog from dismissing and
the id/name from becoming stale on rotation.

In
`@feature/person/src/main/java/com/metasearch/android/feature/person/PersonSideEffect.kt`:
- Around line 16-32: The when on state.sideEffect in LaunchedEffect uses an else
branch which hides unhandled new sealed subtypes; change the catch-all from else
-> {} to null -> {} so the Kotlin compiler can enforce exhaustiveness for the
sealed interface (update the when handling around
LaunchedEffect(state.sideEffect), keeping the PersonSideEffect.ShowToast branch
and the subsequent eventSink(PersonUiEvent.InitSideEffect) logic intact). Ensure
any other similar handlers (e.g., in Graph/FocusingSearch) follow the same null
-> {} pattern.

---

Outside diff comments:
In
`@core/ui/src/main/java/com/metasearch/android/core/ui/component/MetaSearchSquareImage.kt`:
- Around line 15-29: MetaSearchSquareImage now always applies combinedClickable
causing ripples and clickable semantics even when non-interactive; revert to
conditional behavior by gating the modifier: when both onClick and onLongClick
are null, do not apply combinedClickable (or set enabled = false) so AsyncImage
does not get ripple/accessible clickable semantics. Locate the combinedClickable
chained on the AsyncImage modifier and change it to apply only when onClick or
onLongClick is non-null (or pass enabled = (onClick != null || onLongClick !=
null)); retain existing invocation of AsyncImage and null-safe invocation of
onClick/onLongClick.

In
`@feature/detail/src/main/java/com/metasearch/android/feature/detail/graph/GraphDetailPresenter.kt`:
- Around line 56-71: The handler for GraphDetailUiEvent.OnPhotoSelected is
creating a new MainScope() per event which leaks; instead use a single coroutine
scope provided to the presenter (like the scope created via
rememberCoroutineScope() at present() as done in HomePresenter). Change the
logic in the OnPhotoSelected branch to launch on that injected/present-level
scope rather than calling MainScope(), keep using
graphRepository.findMatchedUri(...) and update selectedImages and sideEffect the
same way; ensure the presenter API (present()) accepts/uses a CoroutineScope (or
stores a rememberCoroutineScope result) and that OnPhotoSelected uses that scope
for scope.launch so coroutines are cancelled when the composable leaves
composition.

In
`@feature/detail/src/main/java/com/metasearch/android/feature/detail/person/PersonDetailPresenter.kt`:
- Around line 137-144: The coroutine launched in the
PersonDetailUiEvent.OnConfirmMergeSave handler sets isLoading = true but never
guarantees it will be reset if savePersonInfo() throws; wrap the body of the
scope.launch in a try/finally so that isLoading is set to false in the finally
block (and keep showMergeConfirmDialog = false inside the try after successful
save or set it appropriately on error), optionally catch/log exceptions from
savePersonInfo() before rethrowing; update the lambda that references isLoading,
savePersonInfo(), showMergeConfirmDialog and scope.launch to ensure isLoading is
always cleared.
- Around line 110-119: The TOCTOU bug: capture the null-checked snapshot
`currentPerson` for use inside the coroutine instead of re-reading `person`;
inside the `scope.launch` block replace `person?.inputName` with
`currentPerson.inputName` (and use `currentPerson` wherever `person` would be
read) so the comparison `editName != currentPerson.inputName` and the subsequent
logic (`personRepository.isNameExists(editName)`, `showMergeConfirmDialog`,
`savePersonInfo()`) operate on the stable, previously null-checked value.

In
`@feature/search/src/main/java/com/metasearch/android/feature/search/focusing/FocusingSearchPresenter.kt`:
- Line 140: The when-branch handling FocusingSearchUiEvent.OnColorClick
currently calls TODO(), which throws NotImplementedError at runtime; replace the
TODO() in the FocusingSearchPresenter's event handler with a safe implementation
— e.g. perform a no-op (ignore the event), dispatch a "not yet implemented" UI
effect, or show a toast via the presenter's existing UI-effect mechanism — so
that OnColorClick no longer crashes the app; update the branch inside the
FocusingSearchPresenter (the when handling FocusingSearchUiEvent) to call the
chosen safe action instead of TODO().
- Around line 88-118: The temp file deletion and isLoading reset can be skipped
when the coroutine launched by coroutineScope.launch (assigned to searchJob) is
cancelled; wrap the call to searchRepository.focusingSearch(...) and its
onSuccess/onFailure handling in a try/finally inside the coroutine so that
file.delete() and isLoading = false always run in the finally block (check
file.exists() before deleting and swallow/log any deletion errors), ensuring
searchJob cancellation cannot leak the temp file or leave isLoading true.

---

Duplicate comments:
In
`@feature/search/src/main/java/com/metasearch/android/feature/search/focusing/FocusingSearchSideEffect.kt`:
- Around line 9-32: The composable FocusingSearchSideEffect collides with the
sealed interface of the same name and uses a broad else branch in the when;
rename the composable (e.g., to FocusingSearchSideEffectHandler or
FocusingSearchSideEffectEffect) everywhere it’s used to avoid the type/name
collision, update its function declaration accordingly, and change the when
branch from else -> {} to null -> {} so the when explicitly handles the
absent-case; also update any imports/usages of the sealed interface and the
composable to the new names to keep references consistent and preserve the
existing eventSink(FocusingSearchUiEvent.InitSideEffect) behavior when
state.sideEffect != null.

---

Nitpick comments:
In
`@core/common/src/main/java/com/metasearch/android/core/common/utils/UiText.kt`:
- Around line 12-15: Add a one-line comment above the StringResource class
explaining why it is a plain class (not a data class): state that args is a
vararg Array<out Any> so using a data class would use reference equality for the
args array and break generated equals/hashCode, therefore StringResource
implements UiText as a regular class intentionally to avoid subtle equality
bugs.

In
`@feature/detail/src/main/java/com/metasearch/android/feature/detail/graph/GraphDetailUiState.kt`:
- Around line 16-22: The GraphDetailSideEffect sealed type is annotated
`@Immutable` but exposes a UiText (UiText.StringResource) which contains a mutable
Array for vararg args, violating the `@Immutable` contract; update the
implementation by either removing the `@Immutable` annotation from
GraphDetailSideEffect, or change ShowToast to expose an immutable representation
(e.g., a plain String message or a stable wrapper) instead of UiText, or
annotate/modify UiText/StringResource to be `@Stable/`@Immutable and ensure its
args are stored in an immutable List; target the GraphDetailSideEffect/ShowToast
types and the UiText/StringResource usage and pick one of these fixes so
Compose’s immutability contract is satisfied.

In `@feature/graph/src/main/java/com/metasearch/android/feature/graph/GraphUi.kt`:
- Around line 96-104: The WebViewClient currently unconditionally bypasses SSL
errors in onReceivedSslError by calling handler?.proceed(), which is a security
risk; update onReceivedSslError (in the anonymous WebViewClient) to not silently
proceed: either call handler?.cancel() and surface a user-facing warning/dialog
plus logging, or restrict handler?.proceed() to non-production builds only
(e.g., guard with BuildConfig.DEBUG) and otherwise cancel; ensure the change
touches the onReceivedSslError override and removes the unconditional
handler?.proceed() behavior.

In
`@feature/home/src/main/java/com/metasearch/android/feature/home/HomePresenter.kt`:
- Around line 124-131: Rename the event property offSet to offset in the
HomeUiEvent.OnImageLongClick definition and update all usages (e.g., in
HomePresenter where you access event.offSet) to event.offset to match
Kotlin/Compose naming; additionally, when handling HomeUiEvent.OnLongClickCancel
in HomePresenter (where you currently set selectedLongClickImage = null), also
clear selectedOffset (set it to null) so the offset doesn't remain stale when no
image is selected.

In
`@feature/home/src/main/java/com/metasearch/android/feature/home/HomeSideEffect.kt`:
- Around line 10-11: The composable function named HomeSideEffect conflicts with
the sealed interface HomeSideEffect; rename the composable (e.g., change fun
HomeSideEffect(...) to HomeSideEffectHandler(...)) and update all call
sites/imports to use the new name while leaving the sealed interface
HomeSideEffect unchanged so types and handlers are clearly disambiguated; apply
the same rename pattern to all other *SideEffect composables in this PR.

In `@feature/home/src/main/java/com/metasearch/android/feature/home/HomeUi.kt`:
- Around line 305-348: Remove the commented-out preview data block that defines
sample PersonModel and FaceModel instances in HomeUi (the large commented list
of PersonModel/FaceModel entries); delete the entire commented section starting
with the persons = list(...) and all nested PersonModel/FaceModel entries to
clean up dead preview code and leave only active preview/state setup.

In
`@feature/home/src/main/java/com/metasearch/android/feature/home/HomeUiState.kt`:
- Around line 59-62: Rename the parameter offSet to offset in the
OnImageLongClick data class to follow Kotlin naming conventions; update the
constructor parameter name (val offSet: Offset = Offset.Zero -> val offset:
Offset = Offset.Zero) and then update all call sites and usages of
OnImageLongClick.offset (including any pattern matches, destructuring, or
references) to use the new name so compilation and semantics remain correct.

In
`@feature/person/src/main/java/com/metasearch/android/feature/person/PersonSideEffect.kt`:
- Line 10: The top-level composable function PersonSideEffect conflicts in name
with the sealed interface PersonSideEffect, causing readability confusion;
rename the composable (e.g., to HandlePersonSideEffect or
PersonSideEffectHandler) and update all call sites and imports accordingly so
usages like PersonSideEffect.ShowToast still refer to the sealed interface;
apply the same rename pattern for other side-effect handler composables in this
PR (FocusingSearchSideEffect, GraphSideEffect, NLSearchSideEffect, etc.) to
avoid name collisions and improve clarity.
- Around line 1-33: Extract a generic composable to handle nullable side-effect
objects and reuse it from PersonSideEffect: create e.g. HandleSideEffect<S> that
takes sideEffect: S?, onEffect: suspend (S) -> Unit, and onReset: () -> Unit,
move the LaunchedEffect logic there and call
EventHandler.sendEvent(MetaSearchEvent.ShowToast(...)) from the onEffect lambda
for Person side-effects; then in PersonSideEffect replace the LaunchedEffect
block by calling HandleSideEffect(state.sideEffect, { effect ->
EventHandler.sendEvent(MetaSearchEvent.ShowToast(message =
effect.message.asString(LocalContext.current))) }, {
eventSink(PersonUiEvent.InitSideEffect) }) so the unique symbols
PersonSideEffect, PersonUiState, PersonUiEvent.InitSideEffect, EventHandler and
MetaSearchEvent.ShowToast are retained and duplication removed.